-
Notifications
You must be signed in to change notification settings - Fork 1.5k
OCPBUGS-13547: remove special cases for featureset in rendering #7158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPBUGS-13547: remove special cases for featureset in rendering #7158
Conversation
/retest |
Revert for the cause is being floated here: openshift/ci-tools#3409 I'm also floating #7159 for discussion. |
|
/retest |
1 similar comment
|
/retest |
patrickdillon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused about the relationship between this and #7152. Do we still need this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deleting these three lines is not covered by #7152
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, trying to remove the --feature-set from our render commands. #7152 is more important, but this is also desired
3e6b457 to
e1f2157
Compare
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: patrickdillon The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
last installer change for the cluster-config-operator. MCO may need a rendering flag passed. Adding label. A secondary benefit of this approach is that we now have a way to pass the config.openshift.io resources to rendering without individual flags for each render command. This is a good approach to solving the disparate flag sprawl and moving towards contract stability. |
|
/retest |
|
@deads2k: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
@deads2k This broke the feature gate manifest generation process and I think has broken installations. While the manifest file path you removed here has a full path when it writes out, the paths for the feature gate files found by the generic/path walk approach we have, return a relative path to the rendered path, so when we write out using OriginalFileName it writes the file directly to CWD rather than the original path. Any idea why original file name shouldn't be the absolute path? |
|
@deads2k: Jira Issue OCPBUGS-13547: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged:
These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-13547 has not been moved to the MODIFIED state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This completes the reset for rendering featureset sensitive manifests based on the FeatureGate manifest provided by the cluster-config-operator.